TrustRadius Insights
Telcos have found Kubernetes to be a valuable tool for deploying and managing their legacy telco applications. By converting these …
Overview
What is Kubernetes?
Kubernetes is an open-source container cluster manager.
Recent Reviews
Reviewer Pros & Cons
Pricing
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
3 people also want pricing
Alternatives Pricing
What is Vultr?
Vultr is an independent cloud computing platform on a mission to provide businesses and developers around the world with unrivaled ease of use, price-to-performance, and global reach.
Product Demos
Kubernetes Beginner Tutorial 8 | Step by Step Play with Kubernetes (K8s) Demo
YouTube
Demo: Intro to Rancher container management
YouTube
[ Kube 68 ] Kubernetes RBAC Demo | Creating Users and Roles
YouTube
Kubernetes for the Absolute Beginners - Setup Kubernetes - kubeadm
YouTube
Kubernetes Deployment Tutorial - yaml explained + Demo
YouTube
Product Details
- About
- Tech Details
What is Kubernetes?
Kubernetes is an open-source container cluster manager.
Kubernetes Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(164)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
- Recommendations
Telcos have found Kubernetes to be a valuable tool for deploying and managing their legacy telco applications. By converting these applications into Kubernetes objects, telcos have been able to improve uptime and scalability. The simplicity and speed of Kubernetes make it ideal for managing microservices, enabling easy deployment, service discovery, configuration management, autoscaling, and fault tolerance. This has been particularly useful for organizations like LinkedIn, which has used Kubernetes as an experimental product for building and managing Machine Learning pipelines and accessing GPU clusters. Additionally, Kubernetes is widely adopted as a PaaS solution throughout organizations, solving the problem of immutable infrastructure and providing a low learning curve for users. It offers scalability and reliability, making it suitable for managing developer and customer environments at both departmental and organizational levels. Moreover, Kubernetes excels in orchestration across diverse hardware infrastructures, including data centers and multiple cloud providers. It effectively manages containerization applications consisting of hundreds of containers deployed on physical machines, virtual machines, or cloud machines. This addresses resource allocation and scheduling challenges by creating and tearing down containers based on resource demand. Furthermore, Kubernetes serves as a powerful tool for containerizing on-premises servers for seamless deployment to the cloud. Its versatility and standard deployment through Helm have made it the preferred microservice container orchestration platform for deploying web-based applications. Overall, Kubernetes offers a wide range of use cases that enhance the deployment, management, and scalability of various applications in different environments.
Flexibility in Customization: Many reviewers have praised Kubernetes for its flexibility in choosing networking, storage, monitoring, and other solutions, allowing them to customize their workload according to their needs. This feature has been appreciated by a significant number of users.
Seamless Upgrades: Users have mentioned that Kubernetes provides the ability to upgrade applications to a new version without any downtime, making it seamless and efficient. Several reviewers have highlighted this as a valuable feature of the platform.
High Portability: The high level of portability offered by Kubernetes has been positively acknowledged by many users. They appreciate being able to move their applications to different environments easily.
Complex Application Design: Several users have found designing applications on Kubernetes to be complex and time-consuming, especially when manually writing YAML manifests and validating them for errors.
Steep Learning Curve: Many reviewers have mentioned that the learning curve for Kubernetes is slow due to a large number of objects and new concepts. They suggest adding GUI-based operations to help with tasks like finding latency points or identifying resource-consuming pods.
Difficulty in Troubleshooting and Documentation: Users have encountered challenges in understanding and troubleshooting Kubernetes, particularly for beginners. Some users have also found it difficult to find relevant information as the documentation is scattered. They suggest better documentation and versioning for easier access to relevant information.
Based on user reviews, users commonly recommend the following for Kubernetes:
Consider using Kubernetes for companies with a large microservice environment. Users believe that Kubernetes is helpful for managing complex applications and recommend it specifically for organizations with a significant number of microservices.
Acquire a basic understanding and knowledge of Kubernetes before using it. Users suggest that having some familiarity with Kubernetes before implementation is beneficial in order to fully utilize its features and capabilities.
Utilize specialized support and platforms like Rancher when deploying Kubernetes. Users recommend seeking assistance from specialized companies that provide support for Kubernetes, as well as using platforms like Rancher in conjunction with Kubernetes.
Overall, users emphasize the importance of evaluating specific requirements and capabilities before choosing Kubernetes as the container management solution, acquiring knowledge beforehand, and leveraging external support to enhance the deployment experience.
Reviews
(1-5 of 5)Companies can't remove reviews or game the system. Here's why
April 22, 2022
Kubernetes is the answer but, what was the question?
I deploy & manage telco workloads on top of Kubernetes. These are called CNFs (Containerized network functions) which are legacy telco applications converted into K8s objects & connected via a networking & storage solution of your choice, managed by K8s. Just like every other industry, Telcos are no exception converting all their legacy applications sitting on proprietary hardware & boxes to COTS hardware & software architectures adapted toward cloud technologies. Kubernetes helps us to manage the CNFs efficiently & gives a better uptime as compared to VM-based architecture. I see the scope of flexibility & easy scaling in K8s as compared to any other technology.
- Makes sure that the workload remains UP & running by maintaining the desired state.
- Gives a lot of flexibility in choosing the networking, storage, monitoring, etc solutions of your choice.
- The biggest advantage is to upgrade the application with a new version without any downtime.
- Portability of the code is possible up to a great extent.
- Flexibility gives birth to complexity & therefore designing an application on K8s is also complex.
- Writing Yaml manifests manually & then validating them for errors is a pain that should be worked upon with a solution that can write YAMLs & Helm charts in the background with the user designing the application on a GUI-based sketch. Just like they do in OpenStack.
- The overall approach of operations should be shifted from CLI to GUI-based for ease of use.
- Due to a lot of objects & new concepts, the learning curve is really flat i.e. slow.
- Adding GUI-based operations like finding the exact point causing latency OR showing the POD consuming the highest CPU/RAM would be of great help.
- Upgrade without downtime
- Quick scaling
- Redundancy & uptime
- Flexibility to choose the various CNI & CSI options.
- Reduced downtime by more than 50%.
- Increased upgrade frequency by 30%.
- Avoided management escalations by 45%.
As I said earlier also -
- K8s manage the workloads better as compared to OpenStack in terms of reliability, observability & reachability.
- K8s is not limited to only a single networking or storage solution as compared to OpenStack.
- Networking (which is a key concept) is much simpler in K8s as compared to OpenStack.
- It is possible to upgrade your applications without downtime in K8s but in OpenStack, you either have to divert the traffic or face an outage because you have to delete the whole stack & then recreate it.
- K8s manage the workloads better as compared to OpenStack in terms of reliability, observability & reachability.
- K8s is not limited to only a single networking or storage solution as compared to OpenStack.
- Networking (which is a key concept) is much simpler in K8s as compared to OpenStack.
- It is possible to upgrade your applications without downtime in K8s but in OpenStack, you either have to divert the traffic or face an outage because you have to delete the whole stack & then recreate it.
We have moved almost all the stateless services to Kubernetes so managing the umpty number of services can be so easy. Kubernetes helps us in scaling the services up or down based on business needs. It helps us in upgrading the bunch of clusters with zero to minimal downtime based on the applications. We also moved stateful database services (mostly NoSQL) to Kubernetes to manage a single place and to keep the cost down.
- Scaling the application processes/pods up/down based on business needs.
- Managing the pods from a single source.
- Better security along with different layers of security.
- Orchestrating the pods and the available resources in different machines.
- Easier way to update multiple deployments.
- Better way to manage backups.
- Using the available resources effectively and efficiently.
- Scaling up/down applications at the same time keeping the integrity.
- Each environment can be easily duplicated with minimal effort.
- Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
- Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.
I didn't have too much experience or exposure to OpenShift but I do remember that in certain areas our organization found Kubernetes to be more useful and met our needs in comparison to OpenShift. Although I can't compare, I think it's easier to customize Kubernetes because of CRDs and so than OpenShift. Hence, the management decided to go with Kubernetes.
Kubernetes was used in my organization by a specific department. The business problem it attempted to address was resource allocation and scheduling. Creating and tearing down containers at will dependant on resource demand. These resources provided API services to the front-end website.
- Resource allocation and scheduling.
- Managing container instances and run-files.
- Allowing for infrastructure as code.
- Usability and user friendliness.
- There is no front end and anything attempting to provide a self-service model must be created currently.
- It uses pretty new technologies so there is a relatively steep learning curve.
- The only negative impact would be time lost in research and development.
- It is possible that a lack luster understanding combined with a migration to kubernetes before being ready could lead to disastrous scenarios.
- Mesos, Docker and Amazon Elastic Compute Cloud (EC2)
Kubernetes is a great alternative to cloud hosted expensive solutions. It is extremely well documented and maintained. It is probably the best home-grown solution available for container infrastructure management.
Kubernetes has become the microservice container orchestration platform of choice. All our software deployed into Kubernetes - including public websites.
- Scales extremely well
- Handles proper rolling updates of microservices
- Makes it super easy to establish a proper CI/CD pipeline
- Makes it easy for developers to adopt and therefore use
- Could improve user access. Currently uses RBAC - but depending on your implementation (i.e. Amazon EKS) - setting up permissions and adding users to the cluster that are to use the cluster only is sometimes challenging.
- Security can always be improved
- Hooks for identity management; there are open source projects (i.e. Dex) - would be nice to see these adopted to the mainline
- UI Dashboard needs some major improvments
- Has negated the need to hire people to manage deployment/operations as the development team can now work in a true ‘devops’ manner
- Biggest downtime is less than 5 minutes to upgrade a microservice; usually not even noticed by users
- Improved development cycle due to being able to implement a proper CI/CD pipeline
I used OpenShift v2 - which was pre-Kubernetes. (It now uses Kubernetes under the hood - but keeps it fairly hidden). Kubernetes was a ton more stable and easier to use. No more custom CLI to use in order to script together deployments. No more messy ‘push your entire code base to us’ in order to deploy out.
July 09, 2018
Kubernetes is "the" tool for Docker orchestration
We as an organization have very diverse hardware infrastructure. We have our own data centers and multiple cloud providers. The technologies we use are also again very diverse, we use VMs, containers as well as server-less technologies. When it comes to container technologies we are using Docker and orchestrate it with Kubernetes. In most of the cases, each Business unit have their own Kubernetes clusters for application hosting, and categorize it separately for preproduction and production environments.
- Kubernetes can run anywhere, i.e in in-house datacenters as well as in Public cloud
- Very efficient management of containers and self healing.
- Out of the box Automated deployment and rollbacks. And support for many deployment strategies like blue-green, rolling update and recreate.
- Efficient secret and configuration management
- Understanding Kubernetes is little hard and has a steep learning curve.
- Kubernetes is complex, it has its own concepts called pods, services and deployments.
- Debugging and troubleshooting in Kubernetes is quite hard and requires experience.
- Kubernetes is one of the leading orchestrator for containers and also production ready. Helps use Docker containers confidently in production.
- Eliminates maintenance of Docker container lifecycle and handles it automatically.
- RBAC and Namespaces help is clear isolation and access management to applications and access members of team members to each application in a fine grained manner which boosts the confidence to use docker containers.
- Swarm
Docker Swarm is not as advanced as Kubernetes and there are no out of the box solutions for auto scaling and deployment strategies. Docker swarm doesnot have much experience with production deployments at scale. Swarm has a smaller community, and less frequent releases as compared to the very big Kubernetes Community and its rapid releases.